Metadata for Planimetric data, Yellowstone River Corridor, Custer, Park, Prairie, Richland, Rosebud, Sweet Grass, and Treasure Counties, Montana, and McKenzie County, North Dakota. 2007 Metadata for Planimetric data, Yellowstone River Corridor, Custer, Park, Prairie, Richland, Rosebud, Sweet Grass, and Treasure Counties, Montana, and McKenzie County, North Dakota. 2007

Download full XML Metadata

Identification Information:

Citation:

Originator: Woolpert, Inc.

Publication date: 03/27/2009

Title:

Planimetric data, Yellowstone River Corridor, Custer, Park, Prairie, Richland, Rosebud, Sweet Grass, and Treasure Counties, Montana, and McKenzie County, North Dakota. 2007

Publication place: Helena, MT
Publisher: Montana State Library

Online linkage: https://ftpgeoinfo.msl.mt.gov/Data/Spatial/NonMSDI/Collections/Yellowstone_River_Clearinghouse/Geodatabases

Larger Work Citation:

Title: Yellowstone River Clearinghouse GIS Layers
Online linkage: http://mslapps.mt.gov/Geographic_Information/Data/DataList/datalist_Details.aspx?did={17daa910-aba0-11e3-a5e2-0800200c9a66}

Browse graphic file name: http://docs.msl.mt.gov/geoinfo/Images/Metadata/yell_river_2007.gif

Abstract:

The data set consists of planimetric features from the Yellowstone River project collected from air photos of 2007. They are represented by photogrammetrically complied lines, points, and polygons. All information pertaining to transportation, elevation, utilities, communications, and hydrology were extracted into the geodatabase from natural color 0.03 meter orthoimagery.

The data is split into four ESRI personal geodatabase files, one each for Custer, Park, Prairie, Richland, Rosebud, Sweet Grass, and Treasure Counties, Montana, and McKenzie County, North Dakota The download size of each database is approximately 200 megabytes in size.

Topographic contour data and spot elevation were automatically generated from LIDAR data.

The geodatabases contain the following feature classes and subclasses:
BGGEN -- Building polygons
-- Existing Structure
-- Concrete Slab
-- Courtyard within existing structures
COEQP -- Communications Equipment -- Radio Towers
GDSRV -- Areas where ground is obscured by vegetation
HYLIN -- Hydrography Lines
-- Surface Water Course Drain
-- Ditch Aqueduct Centerline
-- Surface Water Course Centerline
HYSUR -- Hydrography Polygons
-- Surface Water Body
-- Surface Water Course
-- Canal Area
IMFDC -- Improvement Flood Control
-- Dam Centerline
-- Levee Centerline
LFHYPC -- Topographic Contours
-- Intermediate (1-meter interval)
-- Index (5-meter interval)
-- Intermediate Depression Contour
-- Index Depression Contour
-- Intermediate Contour Hidden under a structure
-- Index Contour Hidden under a structure
-- Approximate Intermediate Contour in an obscured area
-- Approximate Index Contour in an obscured area
-- Approximate Intermediate Depression Contour in an obscured area
-- Approximate Index Depression Contour in an obscured area
-- Index contour to be suppressed for elevation annotation
LFHYPCA -- Annotation for Topographic Contours
LFHYPS -- Spot Elevations
LFHYPSA -- Annotation for Spot Elevations
LFTOP -- Islands
TRAIR -- Airfield polygons
TRRRD -- Railroad Centerlines
TRRRDB -- Railroad Bridges
TRVEH -- Transportation Vehicle
-- Road Paved
-- Road Unpaved
-- Road Bridge
TRVEHC -- Road Centerline
UTGENP -- Transmission Line Towers
UTGENT -- Tanks

The Treasure County data as delivered also includes some 500-1000m of information residing in Yellowstone County. The data was extended to ensure a seamless transition from data previously generated within Yellowstone County that did not extend to the county line.

Purpose:

This coverage was created as part of a joint Yellowstone River Conservation Districts Council and U.S. Army Corps of Engineers, Omaha District cumulative impacts study of the Yellowstone River channel and floodplain. The multi-agency interdisciplinary planning study extends 477 river miles from Sweetgrass County, Montana to the Missouri River confluence in McKenzie County, North Dakota. It is specifically intended to support the hydraulic, geomorphic, biologic and socioeconomic analyses that are part of the planning study.

Time period of content:

Beginning date: 10/15/2007
Ending date: 11/02/2004
Currentness reference: ground condition

Status:

Progress: Complete
Maintenance and update frequency: As needed

Access constraints: None

Use constraints:

The Montana State Library provides this product/service for informational purposes only. The Library did not produce it for, nor is it suitable for legal, engineering, or surveying purposes. Consumers of this information should review or consult the primary data and information sources to ascertain the viability of the information for their purposes. The Library provides these data in good faith but does not represent or warrant its accuracy, adequacy, or completeness. In no event shall the Library be liable for any incorrect results or analysis; any direct, indirect, special, or consequential damages to any party; or any lost profits arising out of or in connection with the use or the inability to use the data or the services provided. The Library makes these data and services available as a convenience to the public, and for no other purpose. The Library reserves the right to change or revise published data and/or services at any time.

Point of contact:

Stan Danielsen
Project Coordinator
Yellowstone River Conservation District Council (YRCDC)
1371 Rimtop Drive
Billings, Montana 59105
Telephone: 406-247-4414
Fax: 406-247-4429
E-Mail: sdanielsen@mt.gov

Data Quality Information:

Attribute accuracy report:

Attribution was obtained through the visual inspection of aerial imagery and the interpretation and application of the classification schema. No ground checks were performed after compilation but the data collection approach and inputs were designed to support 90% or better attribution accuracy in the completed dataset.

Completeness report:

Topological and attribute accuracy was verified by visually examining the data in its final format

Horizontal Positional Accuracy Report:

Horizontal accuracy meets or exceeds a 4.5 foot horizontal accuracy at 95 percent confidence level using RMSE(r) x 1.7308 as defined by the FGDC Geospatial Positioning Accuracy Standards

Quantitative horizontal positional accuracy assessment:

Horizontal positional accuracy value: NSSDA
Horizontal positional accuracy explanation:: The National Standard for Spatial Data Accuracy (NSSDA) implements a statistical and testing methodology for estimating the positional accuracy of points on maps and in digital geospatial data, with respect to georeferenced ground positions of higher accuracy.

Vertical positional accuracy report:

Vertical accuracy meets or exceeds a 0.6 foot vertical accuracy at 95 percent confidence level using RMSE(r) x 1.9600 as defined by the FGDC Geospatial Positioning Accuracy Standards

Quantitative vertical positional accuracy assessment:

Vertical positional accuracy value: NSSDA
Vertical positional accuracy explanation:: The National Standard for Spatial Data Accuracy (NSSDA) implements a statistical and testing methodology for estimating the positional accuracy of points on maps and in digital geospatial data, with respect to georeferenced ground positions of higher accuracy.

Lineage:

Source information:

Originator: Eisenbraun and Associates
Publication date: 03/14/2008
Title: Planimetric Map
Type of source media: digital files
Calendar date: 03/20/2008

Process step:

The planimetric dataset's features were photogrammetrically compiled from digital ADS40 aerial imagery, using softcopy workstations. Collected features were collected with 3D linestrings, points and polygons and coded with predefined attributes. The softcopy workstation interfaced with Bentley Microstation where the features were stored, and later underwent a Quality Control review for content and completeness. Once approved these files were then translated into shapefiles using Safe Software Feature Manipulation Engine, where line and polygon topology was built. Finally, the shapefile features were imported into the feature classes of a Personal Geodatabase.

Process date: 03/20/2008

Process contact:

Woolpert, Inc
116 Inverness Drive East, Suite 105
Englewood, CO 80112

Process step:

LiDAR data was acquired using a Leica ALS50 from an average altitude of 3,000-feet above ground level to provide an average ground sample distance of 2.1-feet. First and last return data was collected along with the signal return intensity. Two redundant airborne GPS bases stations were utilized during the data acquisition with maximum line-of-sight distance between the base station and aircraft of 20-km. The LiDAR data was reduced using Grafnav (Waypoint Consulting) for GPS post-processing, PosProc (Applanix Crop) for IMU processing, ALS50 Post Processor (LH Systems) to initial LiDAR processing, TerraScan (Terrasolid) for initial point classification, and proprietary Woolpert developed software for refining the point classification and QC.

The LiDAR data was reviewed in 3D using a digital photogrammetric work station using ADS40 digital stereo imagery. The LiDAR data was filtered into breaklines to separate the mass point. The resulting Digital Terrain Model was imported into Bentley's InRoads site/civil software, converted to a Triangulated Network (TIN) and contours were interpolated at an interval of 1m. The integrity and accuracy of the Digital Terrain Model are depicted by the resultant contours.The InRoads contour files were then clipped into 1200 x 1200 meter grid tiles and imported into a ESRI format geodatabase.

The spot elevation points were collected by querying elevations from a Digital Terrain model made up of LiDAR points and breaklines. These points were then labeled with textual elevation information to supplement the contour dataset and provide elevation information at specific locations. Once collected the spot elevations were recalled at a softcopy workstation interfaced with Bentley Microstation and underwent a Quality Control review for content and completeness. Once approved these files were then translated into shapefiles using Safe Software Feature Manipulation Engine as point features with elevation attributes. Finally, the shapefile features were imported into the feature classes of a Personal Geodatabase.

Process date: 03/20/2008

Process contact:

Woolpert, Inc
116 Inverness Drive East, Suite 105
Englewood, CO 80112

Spatial Reference Information:

Horizontal coordinate system definition:

Grid coordinate system name: State Plane Coordinate System

SPCS zone identifier: 2500

Lambert conformal conic:

Standard parallel: 45.000000
Standard parallel: 49.000000
Longitude of central meridian: -109.500000
Latitude of projection origin: 44.250000
False easting: 600000.000000
False northing: 0.000000

Planar distance units: meters

Geodetic model:

Horizontal datum name: North American Datum of 1983
Ellipsoid name: Geodetic Reference System 80
Semi-major axis: 6378137.000000
Denominator of flattening ratio: 298.257222

Altitude system definition:

Altitude datum name: North American Vertical Datum of 1988
Altitude resolution: 0.010
Altitude distance units: meters
Altitude encoding method:: Explicit elevation coordinate included with horizontal coordinates